chore: standardize repository config - #90
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
❌ Deploy failed
📋 Build log (last lines)🤖 Powered by surge-preview |
|||||||||
|
Warning Review limit reached
Next review available in: 57 minutes Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable usage-based reviews in Billing to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information, and refer to the rate limits docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
Walkthrough仓库配置、文档、示例和 GitHub 工作流更新为新的 Changes发布与文档更新
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #90 +/- ##
=======================================
Coverage 99.16% 99.16%
=======================================
Files 10 10
Lines 239 239
Branches 106 104 -2
=======================================
Hits 237 237
Misses 2 2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request transitions the project configuration, documentation, and examples to the @rc-component/tour package name. Key updates include modifying path aliases in .dumirc.ts and tsconfig.json, updating example imports, adding a Vercel configuration, and revising the README.md documentation. Feedback suggests separating the build step from the publishing tool in package.json to avoid potential infinite loops with prepublishOnly, mapping the ES module path directly to src/index.tsx in tsconfig.json for consistency, and removing a redundant wildcard alias in .dumirc.ts.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
.github/workflows/surge-preview.yml (1)
34-36: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value预览构建建议使用
npm ci以保证可复现性。
npm install可能会改写package-lock.json并解析出与锁文件不一致的依赖版本。在 CI 预览场景下，若仓库已提交锁文件，使用npm ci能保证安装结果可复现且更快。♻️ 建议改动
build: | - npm install + npm ci npm run build🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/surge-preview.yml around lines 34 - 36, The preview build step in the surge workflow currently uses npm install, which can drift from the lockfile and make CI runs less reproducible. Update the build command in the workflow to use npm ci instead, keeping the rest of the build sequence in the same job unchanged so the dependency install remains deterministic when the lock file is present..github/workflows/react-component-ci.yml (1)
11-12: 🔒 Security & Privacy | 🔵 Trivial收紧传递给可复用工作流的密钥范围。
被调用的工作流
test-utoo.yml仅实际使用了CODECOV_TOKEN密钥（通过codecov/codecov-action@v5）。当前使用secrets: inherit会无条件转发所有仓库密钥，违反了最小权限原则。建议改为显式传递仅必要的密钥。同时，@main引用未固定到具体提交哈希，存在供应链风险，建议在条件允许时进行固定。🔒 按需传递密钥示例
test: uses: react-component/rc-test/.github/workflows/test-utoo.yml@main - secrets: inherit + secrets: + CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/react-component-ci.yml around lines 11 - 12, The reusable workflow invocation in the CI job is over-broad because `secrets: inherit` forwards every repository secret, and the `@main` reference is not pinned. Update the workflow call to explicitly pass only the `CODECOV_TOKEN` secret used by `test-utoo.yml` and replace the `react-component/rc-test/.github/workflows/test-utoo.yml@main` reference with a fixed commit SHA to tighten access and reduce supply-chain risk.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Around line 68-78: Update the package.json engines.node constraint to match
the واقعی runtime requirements by raising it from >=8.x to >=12.20. The issue is
in the package metadata around the peerDependencies/engines block, and the fix
should keep the declared Node support aligned with the minimum version required
by typescript and cross-env so installs and runtime checks reflect the actual
supported environment.
In `@README.md`:
- Around line 19-25: The README highlight text uses nonstandard wording:
“builtin” should be “built-in” in the user-visible description. Update the
highlighted feature list wording in the README to read “custom built-in
placements” so the documentation uses standard spelling and remains consistent.
- Around line 62-97: The API table in the README has an inaccurate default value
for scrollIntoViewOptions; update the documentation to match the actual default
used in the Tour implementation. Locate the Tour props/docs entry for
scrollIntoViewOptions and replace the vague “center options” text with the
explicit default object shape { block: 'center', inline: 'center' }. Keep the
existing animated and mask entries unchanged since they already match the
source.
---
Nitpick comments:
In @.github/workflows/react-component-ci.yml:
- Around line 11-12: The reusable workflow invocation in the CI job is
over-broad because `secrets: inherit` forwards every repository secret, and the
`@main` reference is not pinned. Update the workflow call to explicitly pass
only the `CODECOV_TOKEN` secret used by `test-utoo.yml` and replace the
`react-component/rc-test/.github/workflows/test-utoo.yml@main` reference with a
fixed commit SHA to tighten access and reduce supply-chain risk.
In @.github/workflows/surge-preview.yml:
- Around line 34-36: The preview build step in the surge workflow currently uses
npm install, which can drift from the lockfile and make CI runs less
reproducible. Update the build command in the workflow to use npm ci instead,
keeping the rest of the build sequence in the same job unchanged so the
dependency install remains deterministic when the lock file is present.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: bbf0cd73-0d7d-47ec-8279-0cf464fc64fa
📒 Files selected for processing (31)
.dumirc.ts.github/FUNDING.yml.github/dependabot.yml.github/workflows/main.yml.github/workflows/preview.yml.github/workflows/react-component-ci.yml.github/workflows/react-doctor.yml.github/workflows/surge-preview.yml.gitignoreREADME.mddocs/examples/animated.tsxdocs/examples/arrow.tsxdocs/examples/basic.tsxdocs/examples/center.tsxdocs/examples/closable.tsxdocs/examples/customBuiltinPlacements.tsxdocs/examples/customMask.tsxdocs/examples/gap-horizon.tsxdocs/examples/gap-radius.tsxdocs/examples/gap.tsxdocs/examples/inline.tsxdocs/examples/notFound.tsxdocs/examples/open.tsxdocs/examples/placement.tsxdocs/examples/scrollIntoView.tsxdocs/examples/strictMode.tsxdocs/index.mdnow.jsonpackage.jsontsconfig.jsonvercel.json
💤 Files with no reviewable changes (3)
- .github/workflows/preview.yml
- now.json
- .github/workflows/main.yml
|
Deployment failed with the following error: Learn More: https://vercel.com/afc163s-projects?upgradeToPro=build-rate-limit |
|
Deployment failed with the following error: Learn More: https://vercel.com/react-component?upgradeToPro=build-rate-limit |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
1 participant
Summary
Standardize this rc-component repository as part of the Ant Design rc-component maintenance sweep.
Tracking issue: ant-design/ant-design#58514
Scope
types: "./es/index.d.ts", publishConfig, and release flow through@rc-component/np.react-component/rc-test/.github/workflows/test-utoo.yml@mainworkflow, React Doctor, Codecov, CodeQL, updated GitHub Actions versions, and guarded Surge preview fallback.docs-distoutput and remove legacynow-build/ Cloudflare Pages residue.Notes
secrets: inheritis kept untilreact-component/rc-test#176is merged, then it can be narrowed to explicitCODECOV_TOKENforwarding.